Skip to content

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Oct 22, 2025

This also required updating various k8s components to v0.34.1 and using the latest openshift/client-go and openshift/library-go

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 22, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 22, 2025

@tmshort: This pull request references OPRUN-4157 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

This also required updating various k8s components to v0.34.1

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 22, 2025
This also required updating various k8s components to v0.34.1
and using the latest openshift/client-go and openshift/library-go

Signed-off-by: Todd Short <[email protected]>
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 22, 2025

@tmshort: This pull request references OPRUN-4157 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

This also required updating various k8s components to v0.34.1 and using the latest openshift/client-go and openshift/library-go

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@tmshort
Copy link
Contributor Author

tmshort commented Oct 22, 2025

/retest-required

github.com/operator-framework/catalogd v1.0.0-rc1
github.com/operator-framework/helm-operator-plugins v0.7.0
github.com/operator-framework/operator-controller v1.0.0-rc1
github.com/operator-framework/operator-registry v1.48.0

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not bump github.com/operator-framework/**

@camilamacedo86
Copy link

/test openshift-e2e-aws

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2025

@tmshort: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn 34dfa64 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jianzhangbjz
Copy link
Contributor

Test passed. Verify it.

1, build an OCP cluster with this unmerged PR via the cluster-bot
launch 4.21,openshift/cluster-olm-operator#146 aws
jiazha-mac:long_duration jiazha$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2025-10-23-092530-test-ci-ln-lbil9vk-latest   True        False         26m     Cluster version is 4.21.0-0-2025-10-23-092530-test-ci-ln-lbil9vk-latest

2. Run a round regression test. LGTM.
jiazha-mac:long_duration jiazha$ python run_e2e.py --once --binary /Users/jiazha/goproject/openshift-tests-private/bin/extended-platform-tests 
...
[2025-10-23 18:39:56] STDERR:
Writing JUnit report to results/junit_e2e_20251023-103956.xml

error: 5 fail, 34 pass, 6 skip (20m19s)

@jianzhangbjz
Copy link
Contributor

/verified by pass
/lgtm

@openshift-ci-robot
Copy link

@jianzhangbjz: This PR has been marked as verified by pass.

In response to this:

/verified by pass
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 23, 2025
@jianzhangbjz
Copy link
Contributor

/verified by @jianzhangbjz

@openshift-ci-robot
Copy link

@jianzhangbjz: This PR has been marked as verified by @jianzhangbjz.

In response to this:

/verified by @jianzhangbjz

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2025
@camilamacedo86
Copy link

/lgtm

@camilamacedo86
Copy link

/retest-required

@camilamacedo86
Copy link

/lgtm

@openshift-merge-bot openshift-merge-bot bot merged commit a329146 into openshift:main Oct 23, 2025
10 of 11 checks passed
@tmshort tmshort deleted the update-api branch October 23, 2025 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants